Devices

This menu displays the possible payloads/devices that can be configured with Veronte Autopilot 1x. Each panel will allow the user to configure different parameters from the available variety of payloads.

By default, only the Transponder/ADS-B device is added to this menu (as shown in the figure above). However, users can add other devices supported by Veronte Autopilot 1x simply by clicking Add device:

Transponder/ADS-B

A transponder is a device that generates or parses ADS-B messages. This menu allows the user to use/configure a transponder through Custom Messages.

The interface includes different transponder models, depending on the one selected, some configurable parameters are enabled or disabled.

The parameters that appear in this menu and that must be configured by the user depending on the transponder model are explained below:

• Model: The options available in Veronte Autopilot 1x are as follows:

  • Internal Transponder
  • uAvionix Ping 20s
  • uAvionix Ping 1090
  • Sagetech MX Series
  • Sagetech XPS-TR
  • Sagetech XPG-TR
  • Sagetech XPS-TRB
  • Daedalean
  • Internal Remote ID
  • Aerobits TT Series
  • Aerobits TR Series

  By clicking on the button next to the drop-down menu, an "information" dialog window about the selected model will appear. For example:

  

• Custom message: Select the Custom message 0-2 to be used for the information exchange, as it will be automatically filled with the information required by the transponder/ADS-B.

• Control Mode: The user must configure the transponder type:

  • Standby: Silence mode.
  • ADS-B In: To detect external aircraft.

  • ADS-B Out: To communicate with external aircraft. There are 2 different types of information that can be shared:

    • Static information: This information should not change during operation (flight). Depending on the model, it can be configured from this app (1x PDI Builder) or from the app of each transponder.

    • Dynamic information: Information that can change during operation (flight). It is configured from the ADS-B widget of the Veronte Ops software.

  • ADS-B In/Out: To detect and communicate with external aircraft.

• Icao: Unique ICAO 24-bit address permanent for the aircraft, which becomes a part of the aircraft's Certificate of Registration.

• Emitter type: The user should specify the type/category of the vehicle in which the transponder is located.
• Call sign: Communication call sign assigned as unique identifier to the aircraft.

The following table summarizes the options that can be selected for each transponder model in the 1x PDI Builder software:

Model	Custom message	Control Mode					Icao	Emitter type	Call sign
		Standby	ADS-B In	ADS-B Out		ADS-B In/Out
				Static	Dynamic (through Veronte Ops)
Internal Transponder	Not available	Available	Available	Available	Available	Available	Available	Available	Available
uAvionix Ping s20	Available	Available	Not available	Available	Available	Not available	Not available	Not available	Not available
uAvionix Ping 1090	Available	Available	Available	Available	Available	Available	Available	Available	Available
Sagetech MX Series	Available	Available	Available	Available	Available	Available	Not available	Not available	Not available
Sagetech XPS-TR	Available	Available	Not available	Available	Available	Not available	Not available	Not available	Not available
Sagetech XPG-TR	Available	Available	Not available	Available	Available	Not available	Not available	Not available	Not available
Sagetech XPS-TRB	Available	Available	Available	Available	Available	Available	Not available	Not available	Not available
Daedalean	Available	Not available	Not available	Not available	Not available	Not available	Not available	Not available	Not available
Internal Remote ID	Not available	Available	Not available	Available	Available	Not available	Not available	Not available	Not available
Aerobits TT Series	Available	Not vailable	Not available	Not available	Not available	Not available	Not available	Not available	Not available
Aerobits TT Series	Available	Not available	Not available	Not available	Not available	Not available	Not available	Not available	Not available

Camera

Adding a camera will create a default Camera configuration menu.

1. Name: Give a name to the customized camera.
2. Search: Users can also choose a camera from the predefined list of cameras, which will automatically establish the values of the Sensor, Resolution and Lens parameters.
3. Sensor: Defines the camera sensor width and height in mm.
4. Resolution: Defines the camera resolution width and height.
5. Lens: Defines the focal length from the camera in mm.

6. Camera cache: Defines the cache time used to play the selected camera on the gimbal widget.

   • A higher cache might increase the video delay.
   • A lower cache might cause video artifacts or disconnections.

   Tip

   333 miliseconds should be enough for a 1080p video.

7. Cam associated with gimbal: If the camera is from a Gimbal device, it is important to configure this field and select the Gimbal block number that is related to this camera.

8. Photogrammetry: This allows the creation of Photogrammetry actions.

   The actions performed in a Photogrammetry mission can be defined here, following the same possibilities as in Actions - Automations menu.

   • Add Action: Will add a new action.

     Warning

     A maximum of 4 Actions can be defined (Actions 0-3).

   • Generate: Clicking on 'Generate' will create the automation 'Photogrammetry' with a Button as event and with the actions defined here.

An example is given below:

The automation created for Photogrammetry is shown below:

Drop system

Adding a Drop System allows for the configuration of payload release mechanisms, enabling the definition of automated or manual action sequences.

1. Name to the customized drop system.

2. Displays the list of configured actions for the system. Each action represents a specific command or state change for the release mechanism.

3. Defines the type of control or parameter to be modified for the selected action. The following options can be selected: Phase, Output, Navigation, Mode, Periodical, Track, Variable, Features, UserLog, Go To.

4. Sets the desired state for the automation or hardware component depending on the selected parameter.

5. This button adds a new action to the Drop System list.

The actions performed by the drop system can be defined here, following the same possibilities as in the Actions - Automations section.

Board

This board menu allows the user to configure communicate via CAN, in 1x PDI Builder, with another device such as CEX, MEX, MC01, etc., in only 1 step, so in only 1 interface window. Instead of doing it in several steps, as is explained in CEX/MEX - Integration examples section or MC01 - Integration examples section.

• Click on the icon to add a new field. The following parameters must be defined:

  • Commgr: Select the desired COM Manager port: Commgr port 0-5.
  • Can Over Serie: Select the desired Serial to CAN / CAN to serial: CAN Over Serie 0-1 (that is Serial to CAN 0-1 and CAN to serial 0-1).
  • Can Input Filter: Select the desired input filter to use: Input filter 0-3.
  • Can Output Filter: Select the output filter the user wishes to use: Output filter 0-3.
  • Can Port: CAN A, CAN B, CANFD A or BOTH can be selected.
  • ID Can Tx: Enter the ID of the CAN message to be sent.
  • ID Can Rx: Enter the ID of the CAN message to be received.

  Warning

  Be careful not to select a producer/consumer that is being used for another purpose, as the configuration defined here has "priority" and will be changed to this.

  For more information on these parameters, see Input/Output section of this manual.

• Clicking the icon will remove the field and display a confirmation warning message.

• By clicking on 'Apply changes', all these CAN communication settings are applied to the Autopilot 1x configuration.

Below is an example of before/after when changes are applied:

Veronte Gimbal

The Veronte Gimbal menu allows for the integration and communication setup of gimbal systems within 1x PDI Builder.

• Type: Select the Gimbal model from the list of supported devices.

• Gimbal axis type: Defines the mechanical configuration of the gimbal axes: Pan Tilt or Roll Tilt.

• Computer IP: The IP address of the ground station computer receiving the video.

• SLA: Enables compatibility with Sightline Applications protocols for advanced tracking and image processing.

  • CAN Setup: Configures the CAN bus communication:

  

  1. Selection of the CAN bus (CAN A, CAN B, BOTH, CANFD A).

  2. CAN Over Serie 0/1 defines the physical serial port (Serial 0 or Serial 1) used to tunnel CAN bus communication when the gimbal is connected via a serial interface.

  3. TX/RX: Sets the Output/Input filters, CAN IDs, and associated Serial custom messages for data transmission and reception.

  • Variables: This tab allows for the mapping of system variables to gimbal functions:

  

• Command: Mapping of variables used to send control commands to the gimbal.

  

  • Index cam: Assigns a variable to switch between different camera sensors on the gimbal.

  • Palette color: Assigns a variable to change the thermal palette or color display mode.

  • Digital zoom: Maps a variable to control the digital magnification level.

  • Track X / Track Y: Assigns variables to define the screen coordinates or offsets for object tracking targets.

• Telemetry: Mapping of variables to receive real-time feedback and status from the gimbal.

  

  • Optical zoom: Feedback of the current optical magnification level.

  • Track confidence: Reliability score of the current tracking task.

  • Track X / Track Y: Current tracking coordinates from the EO/IR sensor.

• Timestamp: Configuration of time-synchronization variables for data logging. Users can assign specific variables to each byte to define the timestamp structure used in the communication protocol.